home *** CD-ROM | disk | FTP | other *** search
- =----------------------=
- LUNATIX Vers. 4.1a
- =----------------------=
-
- Written by Mike Snyder
- (C) 1995 by N-E-Ware
- -------------------------------------------------------------------------
- This game is Shareware... if you plan to
- continue using it, you are required to
- Register it for $15, And hey... when you
- register... your players can actually win
- the game... Use the REGISTER.TXT form.
- -------------------------------------------------------------------------
- Find the Latest Version of Lunatix From
- The Rolling Eye BBS: 316-733-6365 (Sysops: Mike & Brandon Snyder)
- Danger Zone BBS 405-332-4059 (Sysop: Robert Graham)
- Fidonet 1:3806/11 Magic Name "LUNATIX" (Sysop: Robert Graham)
- Fidonet 1:291/25 Magic Name "LUNATIX" (Sysop: Mark Sheppard)
- World Wide Web: http://haven.uniserve.com/~shane/ (Shane Schlosser)
- FTP: ftp.uniserve.com /pub/bbs_doors
- FTP: ftp.europa.com /outgoing/DOORS/N-E-WARE
- FTP: ftp.ldl.net /pub/bbs_doors/N-E-WARE
- -----------------------------------------------------------------------------
- Lunatix is a DOOR game, which means it was designed soley for the
- purpose of online play. It has been successfully run as a shelled-
- to program from a terminal host mode (by using a DOOR file with
- default settings) but it was designed for play over a BBS. Lunatix
- will read info from a "drop" file your BBS creates.
- -----------------------------------------------------------------------------
- Lunatix Version 3.1a has been released with RIP support. It includes RIP
- screens for the first 4 rooms (the main ones, really) but 16 other "rooms"
- will be read in if they exist (see the structs.doc file). The RIP graphics
- will only show up remotely to the caller... as a sysop, what you will see
- is a bunch of garbage which is the actual RipScrip code. Don't let it
- worry you, if the caller is in RIP mode, they'll see the graphics. :)
- -----------------------------------------------------------------------------
-
- Important info about LUNATIX and its ownership:
-
- HCI, my former employer, has reportedly obtained an *illegal* copyright
- to Lunatix, meaning they supposedly registered this software with the
- copyright office. However, HCI did *NOT* own the rights to the game.
- I was *NOT* hired to develop this game, and I *DID* write 99% of it on
- my own time. I *DID NOT* give my rights to the game to HCI, and in
- copyrighting an earlier version they have severely broken the law in
- a case of software piracy. Anyone supporting HCI will receive no
- support from me, and the earliest version of Lunatix I currently
- endorse is version 3.2a. HCI would have you believe that I *stold*
- this game from them. The opposite is true. In the end, you may
- either support a company who plotted to steal my software, or you may
- support me, who developed this software for your enjoyment.
-
- -----------------------------------------------------------------------------
- Lunatix is now easier than ever to install:
-
- BRIEF OVERVIEW:
-
- You may need to read the rest of the setup steps, but basically
- this is how you install Lunatix. Make a Lunatix directory. Put all
- these files there. Run the INSTALL.EXE program and start at option (B)
- and run each one from there on. Be sure your path names end with a '\'
- symbol, i.e. C:\GAMES\LUNATIX\. Make a batch file that calls Lunatix
- with the node number. If you're on a single node, just LUNATIX N0
- for the default setup you made. For other nodes, use the (D) option
- in the Install to copy/change the setup-0 info to node-1, node-2, and
- so on. Be SURE the Nx command (X=1 would be N1) is for a node setup
- you have actually made. Your batch file must also CD (change dir-
- ectory) into the Lunatix directory, whever you have defined it, and
- set the default drive (especially for networks) to that drive.
-
- Following this is a section on command-line parms and troubleshooting.
-
- For more detailed instructions, read the following steps.
-
- THE LONG VERSION:
-
- 1) First of all, unzip all the main files into a directory on your
- master "server" node, such as C:\LUNATIX... if you're reading this,
- you've probably already done that.
-
- 2) Next, run the INSTALL.EXE program. You need to select every
- option from the main install menu, Except option (D) if you just
- have 1 node.
-
- A) This is how you enter your Registration code once you register.
- B) Setup Lunatix.Cfg -- this creates a configuration file for
- Lunatix, which contains a few Sysop-selectable things, such as
- the Insane Assylum name, max closet fights per day, etc...
- C) Create Linkto.BBS -- this creates a "handle" file between
- Lunatix and the DOOR drop file of your choice. If your door
- format is listed in the Linkto sub-menu, you'll have no
- problem... just select it, then at the prompts enter the
- path to your drop file, your modem setup (N81, E71, or
- whatever), and your IRQ number (0 for default, or a valid
- IRQ value).
- D) Setup Other Nodes -- After you've got the node 0 setup files
- (made with options B and C) you're ready to set up your
- other nodes. It'll ask for the node num to load, you you
- say '0'. Later, you can use this to load and edit any
- available Node setup. Using Option D, you will edit and/or
- save configs for each node you have. Note, if you just have
- a single node but your BBS will be calling at as NODE1, be
- SURE you use this node setup option to copy the original Node0
- setup (which you might not use) over for your *real* node, 1.
- E) Create .DAT and .TXT files -- Builds necessary data files
- F) Reset player files -- Only do this once, unless the player
- files get corrupted... and they might get corrupted if you
- attempt to edit them with a text editor -- although the
- Lunatix player data file is no longer as volatile as it was,
- you can still mess it up if you diddle with it.
-
- 3) Next, add Lunatix to your Online Games (Doors) menu within your
- BBS. A batch file will probably be needed, to change to the
- Lunatix directory then run Lunatix. For example, your BBS may
- call a LUN.BAT (that you make) which might like one of these:
-
- ;for single or master-node
- @ECHO OFF ;don't echo DOS batch commands
- CD C:\LUNATIX ;change to local copy of Lunatix
- LUNATIX.EXE N0 ;run Lunatix as Node 0
- CD C:\RENEGADE ;return to BBS directory
-
- ;for any other nodes (sample)
- @ECHO OFF ;turn DOS command echo off
- E: ;change to BBS Lunatix Drive
- CD \LUNATIX ;change to Lunatix directory
- LUNATIX.EXE N%1 ;run Lunatix as Node %1 (Parm passed)
- ;LUNATIX.EXE N2 ;Could hard-code the node number instead...
- C: ;Change back to its own drive
- CD C:\RENEGADE ;return to BBS directory
-
- If you want to use one batch file to call every node, see the
- SAMPLE.BAT file in this archive for an example on how to do
- this.
-
- When calling Lunatix, REMEMBER to give the node number... LUNATIX N0
- for a single-node system or the first node, LUNATIX N1 for the next
- and so on. It will read the info you setup in the install.
-
- 4) MULTI-NODE OPERATION:
-
- Install Lunatix as described and setup the Node 0 info.
- Pay close attention to any mention for path names. REMEMBER: Path
- names are specific to each node! Nodes may have a common Z: drive,
- which is actually the C: drive on your server... keep this in mind
- and use your own configuration when setting up Lunatix for multi-node
- play. As describe above, use the first configuration for Node 0 and
- use the Node Setup option to edit and save it for the other nodes.
-
- REMEMBER THIS: For multinode operation, it is VERY important that the
- system dates on each node are very close! When the time is very much
- out of alignment, the automatic daily event may be ran more than once.
-
- Also, for multi-tasker users, Lunatix now has time-slicing routines.
- These have been tested unded Windows 3.1 and Windows 95 and should work
- under OS2 as well. It also auto-detects DesqView, however these have
- *not* been tested as of the release of Lunatix 2.0b. To start Lunatix
- in Time Slicing mode, add "SLICE" to the Lunatix command line... along
- with the n<nodenum> you could call LUNATIX N2 SLICE to run Lunatix in
- Time-Slicing mode for node-2. If you have problems in time-slicing
- mode, omit the SLICE command and just try running in standard mode.
- If (especiall for DesqView) it won't work correctly in Time Slicing
- mode, please let me know so I can work on a fix as soon as possible.
-
- 5) Lunatix now has IGM support! See the STRUCTS.DOC file for an explanation
- of the data files, and info about creating your own IGM! NOTE: If you
- create an IGM, it MUST be approved by us before you release it, otherwise
- it will be considered a hack, and we will encourage Lunatix users to
- avoid using it.
-
- The addition of IGM support is meant to increase the ever-growing popularity
- of Lunatix. IGM's will work in an unregistered version of Lunatix. We are
- taking a chance with this, in the hopes that great IGM's will prompt more
- Sysops to register Lunatix, although the IGM's work regardless.
-
- Note: A maximum of 26 IGM's will be read from the IGM.DAT file, so as the
- volume of available IGM's grow, you need to pick the best once to use. :)
-
- Note: Now, there is no need to preserve the DROP file that Lunatix reads.
- When Lunatix gets control, it reads what data it needs and creates
- a MODEM.x with x being the node number... in this manner, it doesn't
- matter if the drop file gets overwritten. It will no longer be
- needed about 1 second after Lunatix gets control.
-
- If you don't have a BBS, Lunatix can still be run in "local" mode
- on your system for evaluation purposes. To do this, install
- Lunatix as normal, using "CALLINFO.BBS" Wildcat door as your Door
- type in the Install LINKTO.BBS configuration. Then, use the
- included CALLINFO.BBS file.... you'll need a text editor to change
- the top line to your name... then the BBS will use this when mapping
- it to another "alias" name you choose. You might keep a backup
- of the sample CALLINFO.BBS file in case your BBS copies over it
- and you wish to run Lunatix in No-BBS local mode. Have the setup
- for a node (such as node 99) point to this "local" drop file, and
- run Lunatix with the node num. LUNATIX.EXE N99
-
- Also, read the LEGAL.TXT file for legal info on Lunatix. The
- LISTING.DAT contains a list of all files that should be included
- within the Lunatix archive -- all must be included, and no more,
- or you received an illegal copy of Lunatix...
-
- Don't let that get you down... because Lunatix is definitely Share-
- Ware... you are free to distribute it as specified in LEGAL.TXT.
- However, we only ask that the original game remain intact with
- no modifications when distributed. Also, when you're installing,
- check out the "Why should I register Lunatix?" option for a few
- good reasons to spend a mere $15 towards the enjoyment of your
- users. :)
-
- About the LUNEVENT.EXE Daily Event:
-
- Many people have pointed out that there was nothing in the docs about the
- daily event and how to set it up. The reason I omitted this is because the
- event is automatic and will be run when the first users plays the next day.
- You do not need to put this in your BBS event -- it is automatic.
-
- -----------------------------------------------------------------------------
- A word of warning. The artwork in 3.2a is my own RIP attempts. Sorry. I
- am a terrible artist, but as Raiden said in Mortal Kombat the movie "There
- is no one else." Of course if any of you out there are RIP artists and
- have a bunch of free time, read the section about external room screens in
- the STRUCTS.DOC file which tells how to name your rip or text rooms for
- Lunatix to use. Plus if you want, I could include them in future versions.
- -----------------------------------------------------------------------------
-
- LUNATIX COMMAND-LINE PARAMETERS
- (an 'x' will show where a number is needed)
-
- Node Specification: (Mandatory, first thing on command-line)
- Format: Nx
- Examples: LUNATIX N0, LUNATIX N1, LUNATIX N15
- Notes: Setup info must be defined for the node-num.
- Install option (D) does this.
-
- Windows/OS2 Time-Slicing: (Optional Command for Win 3.1, Win95, OS2 users)
- Format: SLICE
- Example: LUNATIX N0 SLICE
- Notes: This may improve performance under windows/os2
-
- Clean Mode Option: (Optional Command)
- Format: CLEAN
- Example: LUNATIX N0 CLEAN
- Notes: Will disable the "Flirt-with-Nurse" option
-
- Run in local mode: (Optional Command)
- Format: LOCAL (or LOC)
- Example: LUNATIX LOCAL
- Notes: With Local, you can easily run Lunatix (after
- you have run install to generate config info)
- With or without a bbs. Play at home. Have a
- competition among your family. ;)
-
- You may combine options, such as LUNATIX N0 CLEAN SLICE :)
-
- -----------------------------------------------------------------------------
-
- TROUBLE-SHOOTING:
-
- I will try to provide a little section here for finding problems in your
- setup. This may be very incomplete, but here goes:
-
- Q: After upgrading to 3.2a, it seems that Time Slicing no longer works
- A: Correct. I had to temporarily disable it. It will return, though.
-
- Q: After upgrading to version 3.1a or newer, I noticed that some users
- play and the screens look like weird garbage code or something.
- A: Sounds like the RipScrip. Lunatix now support RIP and that weird
- code is probably the graphics code that a Rip-Terminal will use when
- drawing graphics. Locally, you see the text code, not the graphics.
-
- Q: Why can I not get Lunatix to run correctly with Desqview?
- A: Be sure the FILES= command in your config.sys is large enough... at
- least 75 I'm told. Also, allocate enough memory for the window. If
- nothing works, I don't know what to say. It has been tested under
- DesqView and it runs fine. If it doesn't work for you, the problem
- lies in something else, and without being a desqview user myself, I
- wouldn't know what that is.
-
- Q: It used to run fine with an earlier version, but I just unzipped
- this version and now it won't run right.
- A: Read the UPGRADE.DOC every time you upgrade Lunatix. Many times,
- things were changed and you must know what to do to upgrade.
-
- Q: I have this version set up okay, and I pass in the node number using
- the Nx command line parameter, but when it runs it gives a "Sysop:
- fatal error" and it quits.
- A: It isn't reading all the setup files correctly, and this is almost
- always because something is missing, or wrong, in your setup. Go
- into the INSTALL program and re-make the Linkto.BBS, Lunatix.CFG,
- and the .TXT,.DAT files. Then, use the Node-Setup option to view and
- edit this information or copy it to Node-1 if you don't have a Node-0.
-
- Q: I get the "Sysop: Fatal Error" and I think it's setup okay.
- A: Here are the most common solutions:
- Does your BBS send out the node number that Lunatix has been set up
- to use? Remember that when you install the game, it creates a
- node-0 setup. If your BBS uses node one, then you aren't setup
- correctly. You must edit the node-0 setup and save it as node-1 using
- install option "D". Or, for a 1-node setup, just call LUNATIX N0.
- Does your setup info for the paths to the master node and to the drop
- file have a trailing backslash? They should. Go into the Install
- option "D" and load up the node setup your BBS uses. Items 8 and 6
- should show those paths, and both should end with a backslash.
-
- Q: The game locks up when a player exits the game. It says "...pull the
- covers... " and locks up tight."
- A: This was a problem in earlier versions which I *think* has been fixed.
- It was an IRQ vector release problem. Try running Lunatix in FOSSIL
- mode instead and see it that helps. (hopefully this problem will no
- longer happen. If so, let me know).
-
- Q: It doesn't lock up at exit, but it locks up during points in the game.
- A1: If this is happening to users at 2400 baud or lower, the problem may
- be the "handshaking" type. Use the INSTALL program to edit the config
- and change the handshaking type to "2" instead of "3".
- A2: If this is happening to all users, regardless of speed, use the INSTALL
- program to edit the setup. Make sure the information is correct, and
- you might need to use a FOSSIL driver. That sometimes helps.
- A3: If it locks up when a user hangs up during the game, the problem is
- most likely one of the above, as a carrier-detection exits the
- program upon carrier loss. The system, to the remote user, may freeze,
- so carrier is dropped. If you are SURE that it locks up when the user
- hangs up, and it's not the other way around (user hangs up because it
- locks up) please let me know.
- A4: If it continues to lock up, and you've tried a FOSSIL, you've tried
- changing the handshaking type, and you've checked the config, then
- your problem may be hidden somewhere in another part of your setup,
- such as a problem in your batch file that calls Lunatix.
-
- Q: I've installed IGM's but Lunatix doesn't see them... In fact I don't
- know where you're even supposed to go in the game to find them.
- A: I've been asked this question, and the problem was that IGM support
- Was added with version 2.0a. Prior to this (verson 1-point-anything)
- there were no IGM's and IGM support was not available.
-
- Q: Some of my IGM's are working right with the newest versions of Lunatix.
- A: Two or three times I changed something in the Lunatix setup format that
- required me to re-write the IGM's as well. Many people have upgraded
- Lunatix without upgrading the IGM's. However, I've tried to make them
- Downward compatible... the New IGM's should work with Lunatix 2.3a or
- newever, although the old IGM's might not work with Lunatix 3.0a, for
- example.
-
- Q: Lunatix can't find the IGM's. Not all nodes access that drive using
- the same drive letter. What can I do?
- A: This is easy, though not really obvious. When you install the IGM's,
- and it asks for the path, try leaving out the drive letter. Instead
- of C:\BWL\ try using \BWL\ or for F:\GAMES\KENNY\ try using just
- \GAMES\KENNY\. This way, since your Lunatix batch file should change
- to the Drive that contains Lunatix and the IGM's, there is no need to
- even use the drive letter. This way if Lunatix is on F: for a couple
- nodes, Z: for a different node, and C: for the main machine (all the
- same "actual" drive) they can all find the IGM's without a problem.
-
- Q: Lunatix works great until a user goes to an IGM, and then they
- sometimes turn into a different player.
- A: This sounds like a multi-node problem. Although the setup for each
- node may be identical, you can't get by with just using N0 for every
- node. This is because Lunatix's own drop file is made using the
- Node-number, and if all nodes have the same number, the file will
- get overwritten when the next player enters the game. To correct
- this, be sure each of your different nodes uses a different number.
- Note: You do NOT need to keep the BBS drop file, as once it is read,
- Lunatix creates its own using the node number.
-
- Q: In the West Wing IGM, a player digs in the trash for 5000 Crazy
- bucks, and only finds 1000, or finds 175000.
- A: This is not a problem. A player can find ANYTHING in the trash can.
- The award is determined by the game, not by what is "requested." :)
-
- Q: Lunatix works fine for remote players, but won't run Locally.
- A: Yes it will. Some BBS's seem to have trouble making a drop file
- for local play. The important part is the COM0 line. You can
- always use the included CALLINFO.BBS for local play (as I always
- do during testing) or use your own drop file and change the COM3
- or whatever to COM0. Note: If it doesn't run locally, it could also
- be an indication of some other setup problems.
-
- Q: Nobody is able to get into Dr. Hammers office in the West Wing IGM.
- A: Hehehehehehehe, for a vague hint, say "Hammer's Office Door" to
- Sigmund Freud. Hehehehe.
-
- Q: My BBS does not support any of the 4 supported Lunatix drop files.
- A: If your drop file is a sequential file (line after line) and you
- know which lines have the com port, and graphics mode, the caller's
- name, and the baud rate, your linkto.bbs can be custom-configured
- to work. I'll need a sample drop file, with any help as to which
- lines are which things. Most boards, though, should support one of
- the 4 included types.
-
- Q: If I can't get it to work, can I ask the author for help?
- A: If you have read these docs enough times that you are SURE the
- answer isn't here, then yes, I'll try. However if it *is* something
- covered in these docs, especially one of the "common errors" that I
- have mentioned in several places... But I'll try to help. :)
- Be sure that when logging onto The Rolling Eye and telling me
- about the problem, please tell me what sort of BBS you have, what
- else you use (Desqview, Qemm, etc..) What version of Lunatix you
- have, are you in FOSSIL mode, any info from your setup. The more
- I have, the better your chances of getting some help with the
- problem. What I *can't* help with are the letters that say "Lunatix
- isn't working on my system. What should I do?" Because in response
- I'd have to type this entire document. I also need to know what
- you've tried to do to fix the problem, and what the results were.]
- Any "observations" help also (is it just at 2400 baud, is it only on
- the 3rd node which uses Com2 instead of Com3, etc). This is not
- a guarantee that I can solve your problem, as there are some I am
- still not sure about. I will if I can. If not, just keep going
- over this document, re-install if you have to, maybe it was something
- in your setup. I make no promises that I can help you, only that I
- will try until I decide that your problem is "unfixable" by me.
-
- Q: If I've really read this document several times, and I am SURE that
- my problem isn't covered here... and I am ABSOLUTELY CERTAIN that
- I understand the setup instructions and it's still not working right,
- and I contact the author for help, what will I need to do.
- A: A new program has been included in this version, call REPORT.EXE.
- Use this program to generate a report.dat file that tells exactly
- how your setup is. You can refer to this report when telling about
- your setup. I will most likely ask you to run REPORT.EXE to see if
- it spots a setup problem. If it doesn't, I'll need to look at
- report.dat (as you should too) to see if the reported setup info is
- correct for that node.
-
- Q: When I change something in the setup using the install program, the
- changes are never kept.
- A: It doesn't (as of this version) auto-save your work. BEFORE you exit
- the node setup option, you must use the "S"ave option to save as
- either the same or another node number. Be sure to do that to save
- the changes you make to a configuration.
- -----------------------------------------------------------------------------
-
- Thanks, Credits:
-
- A lot of the ideas for Lunatix came from some very creative people.
-
- I want to give props to Robert Graham of Danger Zone BBS for his help
- with the sysop-side of the screen, as well as numerous ideas and
- bug finding.
-
- Also, thanks to Ray Brister for a lot of creative help in this
- game's infancy.
-
- To Casie Graham (for the "map" idea among other things).
-
- Frank Luke, thanks for the Murderous Rampage idea that was added
- in version 2.2a.
-
- Thanks to Blood Doll for liking Lunatix enough to write the first
- 3rd-party IGM.
-
- Thanks to Ed Mullins for asking me to put a "players currently online"
- option and a "stay in an igm" option into the game, for finding
- some of the bugs that keep turning up in the game, and for the
- algorith to auto-detect RIP (yes, I did not know how to do it) :)
-
- Thanks to Jeff Sumberg for his very amazing QBSerial COM library for
- QuickBASIC, without which I'd never have even tried to write a door.
-
- Thanks to Andrew Welch for posting his C++ Time Slicing code in the
- DoorGames echo on Fidonet. I have converted it to BASIC, so Lunatix
- now releases time-slices under Windows, Windows95, and OS2 (With
- the command-line parameter SLICE specified).
-
- Thanks to my Beta Testers. I'm just starting to set up a method to
- get my games tested by someone other than myself. :)
-
- Special thanks goes to Paula Stout, for keeping me happy and inspired
- while I wrote the first few versions of this game, and also (in a
- depressing sort of way) for inspiring the Black Widow's Lair IGM. ><
-
- Most of all, thanks to the many many players and sysops out there who
- have been a great source of inspiration by telling me what a great
- game it is... :) And for helping spot obscure bugs and mistakes in
- the program, and for helping me make it more compatible with a wider
- range of platforms. Thanks.
-
-